-- card: 6430 from stack: in.6
-- bmap block id: 6849
-- flags: 0000
-- background id: 3411
-- name: Alert Types
----- HyperTalk script -----
on closeCard
end closeCard


-- part 1 (button)
-- low flags: 00
-- high flags: 0001
-- rect: left=16 top=85 right=294 bottom=198
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: 


-- part 3 (field)
-- low flags: 01
-- high flags: 0000
-- rect: left=78 top=71 right=285 bottom=498
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 0
-- font id: 3
-- text size: 10
-- style flags: 0
-- line height: 13
-- part name: 


-- part contents for background part 21
----- text -----
Alert Boxes

-- part contents for background part 30
----- text -----
9

-- part contents for card part 3
----- text -----
The purpose of an alert is to notify the user whenever an unusual situation occurs.

An alert box looks like a modal dialog box, except that it's somewhat narrower and appears lower on the screen.  An alert box is primarily a one way communication from the system to the user; the only way the user can respond is by clicking buttons.  Therefore alert boxes might contain dials and buttons, but usually no editable text fields, radio buttons, or check boxes.

How the buttons in an alert box are labeled depends on the nature of the box.  If the box presents the user with a situation in which no alternative actions are available, the box has a single button that's labeled OK.  Clicking this button means "I've read the alert."  If the user is given alternatives, then typically the alert is phrased as a question that can be answered "yes" or "no."

The preferred (safest) button to use in the current situation is boldly outlined.  This is the alert's default button; its effect occurs if the user presses Return or Enter.